Every new Date() re-tested IsConstructor and entered the generic Engine.Construct — call-stack push/pop, recursion-depth compare — although the resolved constructor is already version-validated by the global identifier cache and its verdicts are immutable per instance. The stopwatch row pays this 171k times per op.

JintNewExpression now remembers the last constructor object it constructed through (monomorphic, ReferenceEquals-validated — identity pins the realm and the per-instance verdicts):

• An identity hit skips the IsConstructor type-test.
• When the cached constructor is additionally a zero-argument leaf built-in — a new internal virtual Function.IsZeroArgLeafConstructor, overridden by DateConstructor only when the engine runs the exact stock DefaultTimeSystem — the construct bypasses Engine.Construct entirely. Such a constructor runs no user-observable code and cannot raise a JavaScript error, so the call-stack frame is dead weight. Derived or custom time systems keep the frame (a throwing GetUtcNow would otherwise lose its new Date() stack entry), as do debug-mode engines and suspendable frames; LastSyntaxElement is still set so a .NET-level failure resolves its script location.
• A miss (callee reassigned, another engine sharing the prepared node) falls through to the generic path and re-caches — never a permanent decline (the Re-resolve slot locations when a shared handler tree changes function instance #2616 pattern).

Scope is deliberately Date-first: the mechanism is general, but Error captures the stack (never leaf) and other built-ins aren't exercised by any row today.

Six pins in NewExpressionCacheTests: realm-prototype identity over a warmed call site, mid-script Date reassignment picked up at a warm site, subclass newTarget prototypes, two engines alternating over one shared prepared script, custom-ITimeSystem clocks served through the generic path, and a throwing custom time system surfacing its exception per construct.

Benchmarks (before/after, same machine, sequential)

Stopwatch rows moved within their single-launch mode bands in both directions (classic Execute −1.1%, classic ParsedScript +5.5%, modern flat; the mechanism's expected row share is only ~2%, inside the bands — the isolated driver row above is the evidence; row certification comes with the next EngineComparison refresh). PreparedAnomaly rows: times ±3..7% mixed-sign, allocations +10–20 B/op from the two new fields on JintNewExpression handler instances (fresh-engine-per-op hosts rebuild handlers each op) — disclosed, negligible.

Gates: Jint.Tests 3,295+3,232 pass (6 new pins), PublicInterface 82×2*, Test262 99,426 pass / 0 fail (exact baseline).

* the net472 TimeSystemTests.CanUseTimeProvider wall-clock-tolerance test currently fails on this machine on unmodified main as well (verified 3/3, ~7 ms past its 100 ms window, post-sleep timer state) — environmental, not attributable to the change; the net10 arm and all other net472 tests pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BY8HoKam5H8vTPn1bMY2Hv